Support for TSConfig Paths#34
Merged
ncalteen merged 32 commits intogithub:mainfrom Feb 15, 2024
ncalteen:main
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR primarily adds support for TypeScript actions that make use of TSConfig paths.
Previously this was not functioning due to TypeScript attempting to resolve modules based on this project's
tsconfig.jsoninstead of the one used by the action itself. This is implemented by changing the structure of this project to do the following:binmap inpackage.jsonnow maps thelocal-actioncommand to a basic shell script,bin/local-actionbin/local-actionscript invokessrc/bootstrap.jsbefore the entrypoint of this project is calledsrc/bootstrap.jsscript loadstsconfig-pathsand registers any paths set in the called action'stsconfig.json.Though there shouldn't be any "breaking" changes, the rather large changes in functionality warrant a major version change.
Additionally, a number of code quality/cleanup tasks were completed:
.env.example).tsxfromts-nodeand remove prerequisite.proxyquireand module loading.Closes #33